Manage Workspace and Dataset in Power BI
Dynamic reports are reports in which the data can be changed by a developer according to user specifications. Dynamic reports are valuable because a single report can be used for multiple purposes.
We can use what-if parameters in multiple situations, such as to determine the effect of increased sales to deeper discounts, or to let sales consultants see their compensation if they meet certain sales goals or percentages.
Gateway software acts like a bridge; it allows organizations to retain databases and other data sources on their on-premises networks and access that on-premises data in cloud services, such as Power BI and Microsoft Azure Analysis Services.
A gateway facilitates quick, behind-the-scenes communication that flows from a user in the cloud to our on-premises data source and then back again to the cloud.
Two types of on-premises gateways are:
Organization mode - Allows multiple users to connect to multiple on-premises data sources and is suitable for complex scenarios.
Personal mode - Allows one user to connect to data sources. This type of gateway can be used only with Power BI and it can't be shared with other users, so it is suitable in situations where only one in organization who creates reports. We will install the gateway on our local computer, which needs to stay online for the gateway to work.
Promotion - Promote datasets when they're ready for broad usage. Power BI Admins have permissions to promote datasets.
Certification - Request certification for a promoted dataset from an admin user that is defined in the Dataset Certification tenant admin setting. This certification adds another layer of security for datasets. Certification can be a highly selective process, so only the truly reliable and authoritative datasets are used across the organization.
Query caching
Query Caching is a local caching feature that maintains results on a user and report basis. This service is only available to users with Power BI Premium or Power BI Embedded.
When using query caching, the query results are only specific to a user, and we can only use query caching on a specific page of a report. Several benefits to using query caching include:
Improvement of the performance of reports, dashboards, and dashboard tiles by reducing loading time and increasing query speed; this notion is especially true for datasets that are not refreshed often and are accessed frequently.
It respects bookmarks and default filters, so even if you enable query caching, any bookmarks that you have created still exist.
Cached query results are specific to the user.
All security labels are followed.
It reduces the load on your dedicated capacity because query caching allows for usage of dedicated capacity and not on the dataset.
Comments
Post a Comment